Adds versioned payment settings API (v20260427)#365
Merged
Conversation
Introduces a new `v20260427` API for payment settings
mattnichols
approved these changes
Apr 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira: MC-11798
Summary of Changes
Introduces a new version of the Payment Settings API,
v20260427, changing the list of settings from the 'challenges' property to a 'settings' property.Public API Additions/Changes
com.mx.path.model.mdx.model.payment.v20260427.Settings, is added to represent the payment settings for this specific API version.PaymentBaseAccessoris extended with two new methods:AccessorResponse settings20260427()AccessorResponse updateSettings20260427(com.mx.path.model.mdx.model.payment.v20260427.Settings settings)These methods expose the new versioned API through the gateway, allowing consumers to retrieve and update payment settings for
v20260427.PaymentsController'sgetPaymentSettings()andsetPaymentSettings()endpoints now support API versioning, enabling requests to be routed to either the default or thev20260427implementation based on theAcceptorContent-Typeheader.